Keep in mind that a -h timer (high resolution) could trigger out of order, or within the same $ticks as the last timer call. The high res timer has a resolution much higher than ticks (weird huh?)-- ticks are only accurate to ~10-15ms, whereas a high-res timer is accurate to 1-2ms I believe. Anyway, if $ticks is the same when a new timer fires, your older timer won't fire, possibly causing a race condition and not triggering the command either.
In short, you shouldn't rely on $ticks to seed a high-res timer. Removing "$+ $ticks" and letting mIRC generate its own timer names seems to work just fine for me. Even if there is no race condition, you won't want to seed with $ticks, so you should remove it.
