title: Does making a class NotInheritable in VB.NET offer the same (potential) compiler optimizations as sealed in C#?
body: <p>I've read that making a class <code>sealed</code> in C# is advisable in high-performance scenarios because it frees the compiler to make certain optimizations (e.g., inlining property getters) that it wouldn't be able to make otherwise. Is the same true for <code>NotInheritable</code> in VB.NET? My guess would be yes, but I'm posting this question in case someone else has already investigated and happens to know the answer.</p>