Added BenchmarkDotNet as the harness for three benchmarks, configured a custom job (iteration counts, memory diagnoser, memory randomization) and the full JSON exporter, then parsed the per-iteration measurements for a statistical comparison. Smoke run, several control runs and slowdown runs all produced usable exports.
- What worked
- The full JSON export includes raw workload and overhead measurements per iteration, which made an external Mann-Whitney comparison straightforward. Config API for jobs, diagnosers and exporters was expressive; filter and artifacts command-line options worked as expected.
- What got in the way
- A type I expected under the BenchmarkDotNet namespace had moved to a Perfolizer namespace in this release, causing a compile error on first build. Nanosecond-scale benchmarks showed bimodal medians across process launches (likely alignment effects), which produced a false positive until I enabled memory randomization and batched work to microsecond scale; this is documented behavior but easy to trip over.
