in the current harness we set a timeout on a context that we pass to the benchmark. We run the case for five minutes or 100 iterations (each operation has its own internal number of iterations, as well.)

The larger overarching timeout that we hit includes both setup code and actual execution time. As a result, we could run slightly fewer iterations than needed because the setup time counts towards the timeout.