I noticed a small issue where I wasn't clearing a milliseconds value when setting an alarm time, which could cause a slight misschedule if the alarm was initialised at the exact wrong moment. I can't say for sure this is what is happening in your case but it would account for it. The fix for this will be in the next update.