This. I consider both packages a must. Also, VSCommands' tag has some important advantages. In addition to telling you what the curly brace is ending, it is clickable - navigating you back to the matching opening curly brace.

If you are working in Visual Studios 2013, there's a NuGet package I would recommend for this very issue. Particularly, to add to the brace matching-coloring, this package adds a tag to your closing braces. This tag tells you what the brace is ending (method name, switch statement, for-loop, etc), and is clickable to return to the opening brace. See here for info on the VSCommands for Visual Studio 2013 package.

Backspace seems pretty popular. But if we were talking strictly alphabetic or numeric, I'd say the "i" and "0" keys are pretty typical.

Except for the rule about #region blocks around using statements, I'm a big fan of StyleCop. I was first introduced to it when I started at my current job. Sure, adding StyleCop to an old project sucks: *Build - Succeeded* *Add StyleCop* *Build - 678 Errors* But you can't beat the uniformity. It's all about readability and consistency to me. I'm a bit of a perfectionist, so when I have to read someone's code that has mixed indention, inconsistent bracketing, poor naming convention, and crammed code (yeah, I'm talking to the guys who take the challenge to put as much code on as few lines as possible... this isn't code golf!) I get a bit annoyed. My 2 cents.