For info: Windows timing resolution

[tomdeakin]

If you compile the code with VS2013 or lower, the timer resolution is not fine enough to collect accurate results [1]. You would expect to see minimum timings of zero, and very large memory bandwidths in this case.

This should be fixed in VS2015.

[1] https://connect.microsoft.com/VisualStudio/feedback/details/719443/c-chrono-headers-high-resolution-clock-does-not-have-high-resolution