Added the replicatedmap stabilizer test

I figured out what you mean. Currently I don't think it serves a lot of purpose; logging performance information on a remote member is not adding a lot of value. In the future we'll be adding multiple probes in a test and then we can create a probe for every type of operation and keep track of it (if we want it).

Apart from that it doesn't add a lot of value since operations are done in a certain ratio. Imagine doing 10% of the time a put and you executed 1000 operations (see the operations field), then you have done 100 puts. So the number of different operations is something that can be calculated; doesn't need to be tracked explicitly.