This is just being picky, but the final note is not quite true: the using block also causes the IDisposable object to go out of scope, which the try...finally block does not. It is legal (but very stupid) to write:
IDisposable x = ...;
try
{
...
}
finally { x.Dispose(); }
x.Read();
Which you cannot do with the equivalent using block.
Still gets a five though

I was not aware of this until fairly recently, when I ran some old code through VS 2010's code analysis. I researched the issue and realized what I did wrong. Most definitely something that is too often left out. :-P