UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36

Steps to reproduce the problem:
1.Run the test program http://www.taccgl.org/issues/timer.html
  containing the following code
      var t,i=0,p=0,s="";
      while (i<100) {
		   t=window.performance.now();
		   if (p!=t) {s+="\n "+(t); i++}
		   p=t;
		   };
      console.log(s);
2.Look at the console output in developer tools 
3. 

What is the expected behavior?
The printed timer values (in ms) should have a precision of 5us. So some
of the values should not be integers or close by. 
In Firefox for example values roughly increase in incements of 0.005.

What went wrong?
Sample test output is 
 77.995
 79
 79.995
 81
 81.99500000000002
 82.99500000000002
 84
 84.995
 86
 86.995
 87.995
 89.995
 91.00000000000001
 91.995
 92.995
 93.995
 94.995
...
All numbers are either integers or nearby (differ at most  5us from an integer)

Did this work before? N/A 

Chrome version: 49.0.2623.87  Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 21.0 r0

According to  Issue 506723  the timer resolution should have been
reduced to 5us. However, it seems that the resolution is now
as bad as 1ms.