Well, we had this discussion in the channel before, and the problem I was encountering with high resolution timers is they would occasionally drift away from system time, and so you would get two minute events triggering in the same minute anyway, causing two logged events happening in the same minute (the minute exists twice on paper).
Indeed, I hadn't thought about the scenario you logged where 3 events happen in that 61 second span of time. So basically whether I use a HH:nn or a -h timer, I need to do more checking still to make sure there's only one event per system minute and elapsed minute.
Doesn't using -h cause mIRC's CPU to spike quite a bit?
