The executor bundles both the methods for executing before and after and the
benchmark iteration executor.
The standard use case for an Executor is to execute or obtain the iteration
measurements in a different way (e.g. xdebug, blackfire), the executeMethods logic
has nothing to do with this and so this awkward base class is required.
To be refactored...