Feature/benchmarks/master

I'm not crazy about this.

I think it is better to ask the TestContext for a probe. This can be done in the worker so that each worker gets its own probe. With this approach you are forcing a threadsafe probe to be used. 

Apart from that I would not use the parameters in the set method for it. It only leads to additional code. If you already would go for injected property, I would suggest doing it like this:

```
class FooTest{
@Probe("set") 
SimpleProbe setProbe;

}
```

This is:
* in line with the other properties we inject.
* less code
* in line with normal DI approach