Test oplog stone behavior with very very large oplogs

We have seen an instance where a very large oplog resulted in increasing memory usage (leak) – the suspicion is that the truncate call is somehow leaking memory. We should write a test that exercises very large truncate ranges and see if we can reproduce the behavior.