Monitor benchmark results over time

[wkearn]

As of #130, we can instrument our test code to output profiling information that we can ultimately use to monitor changes in the performance of our library. To do that, however, we need

• to be able to run the benchmark code regularly in a relatively stable environment,
• to aggregate the profiler results over time, and
• to display these results in a useful format (possibly on the documentation site).