As you can read in the documentation for Rhino Mocks:

There are times when the returning a static value is not good enough for the scenario that you are testing, so for those cases, you can use the Do() handler to add custom behavior when the method is called. In general, the Do() handler simply replaces the method call. Its return value will be returned from the mocked call (as well as any exception thrown). The handler’s signature must match the method signature, since it gets the same parameters as the call.

There are quite a lot of delegates defined in Rhino.Mocks.Delegates but none of them has an output parameter so we got stuck when we tried to mock a method with the following signature:

bool TryGet(int id, out Entity entity);

Luckily enough it didn’t take too long before i realised we could simply define our own delegate:

delegate bool TryGetMethod<keyType, ValueType>(KeyType key, out ValueType value);

And now we can easily setup a result for our method:

myEntityRepository
  .Stub(repository => repository.TryGet(0, out myEntity);)
  .IgnoreArguments()
  .Do((TryGetMethod<int, MyEntity>)delegate(int id, out MyEntity entity)
  {
    entity = new MyEntity();
    return id == 1;
  });

As the documentation for System.Diagnostics.Stopwatch says:

In a typical Stopwatch scenario, you call the Start method, then eventually call the Stop method, and then you check elapsed time using the Elapsed property.

I find it a shame that they didn’t provide a method that covers this particular scenario so i did it myself:

public static class Stopwatch
{
 public static TimeSpan Measure(this Action action)
 {
  var stopwatch = new System.Diagnostics.Stopwatch();
  stopwatch.Start();
  action.Invoke();
  stopwatch.Stop();
  return stopwatch.Elapsed;
 }
}

Consuming this method is as simple as:

var duration = Stopwatch.Measure(() => FindElement(10000));
Console.WriteLine("It took {0:0} seconds.", duration.TotalSeconds);