PS, Rock, your test may be inaccurate,

Timers are likely initiated on a queue basis in Windows, so the timer to stop the first timer may likely never be triggered before the first timer finished, not to mention if the claim is that timers are not being accurate, the 1000ms timer wont be any more accurate.

To be safe, you should not use /timer to test the accuracy of your /timer... $ticks would be better

//unset %test | %start = $ticks | echo -a Timer start: %start | timerTEST -cm 1000 1 set %test $!ticks

then check $duration($calc(%test - %start)) when the timer ends

Code:
alias testtimer {
  unset %test 
  %start = $ticks
  echo -a Timer start: %start 
  timerTEST -cm 1000 1 set %test $!ticks
}


//echo -a $calc((%test - %start) / 1000)

I get 1.014, which is (approximately) in seconds, which is close enough to one second between the first trigger and last trigger of the timer.. makes sense.

What's weird is that using -mh (the supposedly high res timer) executes in FIFTEEN seconds, not one.. hmmmmm