Alright, that is absolutely bizzare. Well, unless somebody else can reproduce the problem I'm thinking it's probably more something locally that you're having an issue with. The only question I've got... when the clock opens automatically, does it show the time that the alarm is supposed to be running, or does it show the next minute? i.e. if the alarm is set for 14:57, when the clock opens does it show 14:57, or 14:58?

I'll throw some extra code into the next release just in case so that when the clock opens it will automatically check to see if the current time lines up with one of the programmed alarms; it should be unnecessary (and in most other people's cases it seems to be) and might not be as accurate but it should at least solve your problem there LAB (as long as the time on the clock lines up by the time it finishes loading that is).