Strange measurements when reproducing issue 5650

[SomeDude]

On Friday, 27 April 2012 at 14:14:37 UTC, Steven Schveighoffer 
wrote:
> Have you tried measuring the code timings just inside main 
> instead of the full execution of the program including runtime 
> startup and shutdown?
>
> -Steve

OK, it seems you are right. It turns out using 
Measure-Command{...} was a rather poor way of measuring runtimes 
because of startup/shutdown.

Using StopWatch, I now get consistent results, i.e nearly the 
same times with or without the writeln, but always slightly 
faster without. So all is sorted now.
Thx again.