Alarm Clock takes CPU time up to 3% almost continuosly

I've just installed the latest 0.9.17 version of Alarm Clock and I set it to start upon login in (logical, otherwise why one need an alarm clock).

What I've noticed (never paid attention before) that it uses CPU time from 1% to 3% almost continuosly. The Alarm Clock process runs about each 1 second and runs up to about 5-6 seconds. And all I set up where 3 Birthdays distant for several months one from another.

Now, even if multiple alarms are set, I hardly imagine somebody needs an alarm clock being precise up to a second.

Well, I could imagine such a need, if one sets up a timer, but even this with a little exaggerated imagination. If you disagree with my reasoning for timers, then I think it would be possible to make Alarm Clock being aware of such a need and only in such cases make it checking the time so often (if this is the reason for it using CPU so much), wouldn't it?

BTW, I compared it with the evolution-alarm-notify and this one sleeps practically all the time, though I do have quite a number of appointment alarms set.

So, the question is, is there really need to use CPU time so much and so often?

Do you think, I should report it as a bug instead of a question?