Generate baseline performance measurements for current field arithmetic implementations

[unzvfu]

In order to measure performance improvements, and protect against performance regressions (while refactoring, for example, see #68), we should measure the performance of the current field arithmetic implementations in a way that makes it easy to compare to future performance measurements. The (already in use) Criterion crate seems to cover this functionality, at least for micro-benchmarks such as field operations.