Add method or option to profile / compare performance of scribbler implementations

[benkrikler]

Imported from gitlab issue 2

When writing a scribbler there are often many ways to implement what it does. It's hard to know in advance which method will be the most performant so it would be useful to have built-in (but deactivated by default) performance checks, to help when writing a new scribbler.

[benkrikler]

From the scikit-hep gitter channel this package might be useful: https://github.com/airspeed-velocity/asv for tracking performance.