I'd like to run a benchmark that requires initializing a threadpool before the benchmark and closing it after the benchmark.
Currently, it seems to be impossible to exclude the initialization / closing overhead from the timings collected by Benny.

Could you please enable this use case?
You could do it by accepting optional "setUp" and "tearDown" functions in the add method.