Verified: TCC 14.03.54 Windows XP [Version 5.1.2600]
I also noted that TIMER /S start the timer if it was not running already.
I further noted that REDIRECTING standard output from the TIMER command works only when the command STOPS the timer. For any other mode the command output goes to the screen, even when redirecting both standard output AND standard error.
Lastly, I think the documentation should display the command syntax thus:
TIMER [/1 | /2 | /3] [/Q] [/S | ON [command] | OFF | [command] ]
This applies both to the quick help and the help page, and is intended to indicate that
1/ options /1, /2 and /3 are mutually exclusive, but independent from the other groups
2/ option /Q is independent of all other options (but it makes no sense when combined with the /S option)
3/ options /S, ON and OFF are logically mutually exclusive (though /S combined with ON or OFF may not be reported as errors, but the effect of combining two or all three do not result in a dependable operation); specifying command to be timed is valid only when the ON option is used either explicitly or implicitly, but not when either the /S or the OFF option is used.
My current tests indicate that executing TIMER OFF /S when timer 1 is already off starts it; executing it when it is running the OFF is ignored, regardless of the order of the options. Combining all three options /S, ON and OFF the outcome depends on the order of the options and the current state of the timer. I did not go through all 24 combinations of multiple option selection, option order, and previous timer state. IMHO it would be best if the parser would declare any combination of these options to be error.