This benchmark is going to be skewed since no work needs to be done after the first pop. You might need to add a method to `BenchHarness` that lets you install a "tear-down" that runs after each iteration to reset the state.... not quite sure.