Oh, and as for the spec...I think I like what you originally had (`expect { }.not_to raise_error`) better than `expect(dbl.inspect).to eq('blah')`.  The problem was with resetting, right?  I like that the former makes that implicit, and if `reset` really is a no-op for this case, than `expect { }.not_to raise_error` is fine.  All that said, I think an even better fix would be to do something like:

``` ruby
it "does not affect other objects when a simple stub is reset" do
  dbl = double(:inspect => 'blah')
  reset dbl
  # do something else that behaves wrongly w/o this fix
end
```

I'm not sure what that "something else" is, though, as I still don't quite understand how this affects other things.