some benchmarks use low resolution timers

[cowboyd]

I'm not quite sure why some of the tests use benchmark.js and other not, but on my machine, the baseline-handlebars-list yields the following dataset:

[ 4, 2, 2, 1, 2, 2, 3, 2, 2, 3, 3, 1, 2, 3, 2, 2, 2, 2, 3, 3, 2, 2, 3, 3, 2, 1, 1, 1, 2, 2, 1, 2, 2, 2, 2, 3, 2, 2, 2, 3, 3, 2, 3, 2, 2, 3, 3, 3, 2, 3, 2, 3, 2, 3, 2, 3, 2, 2, 3, 2, 3, 2, 2, 2, 2, 2, 2, 3, 3, 3, 3, 2, 3, 2, 2, 3, 3, 2, 2, 2, 2, 2, 3, 2, 3, 3, 3, 3, 3, 3, 3, 3, 2, 2, 2, 3, 2, 3, 3, 2, 3, 2, 2, 3, 3, 3, 2, 3, 2, 2, 1, 3, 3, 3, 2, 2, 2, 3, 2, 2, 2, 2, 3, 3, 2, 2, 3, 3, 2, 3, 3, 1, 3, 2, 3, 2, 3, 3, 3, 3, 2, 3, 3, 1, 3, 2, 3, 3, 2, 3, 2, 3, 2, 2, 2, 3, 3, 3, 2, 3, 3, 3, 2, 3, 2, 2, 2, 3, 3, 2, 3, 3, 3, 4, 2, 3, 3, 2, 3, 3, 3, 3, 2, 3, 2, 3, 3, 2, 3, 3, 3, 2, 3, 2, 3, 2, 3, 2, 3, 2, 3, 2, 3, 3, 3, 3, 2, 2, 2, 2 ]

When it comes to measuring the difference in performance between ember versions, having only one significant digit drops a lot of information on the floor.

[stefanpenner]

@cowboyd benchmark.js test are a new addition for the micro-level tests, I would like to push them to the macro tests aswell