Custom FxCop Rule - Do not use GOTO Statements

This custom FxCop rule enforces the idea of not using VB Goto
statements in your code - never a good programming practice.

To determine if we have GOTOs in the MSIL (intermediate language), we need to
look at the OpCodes. This can be done with any
dissasembler. The opcode for a GOTO is an unconditional
branch. Looking at the IL you will see br.s
instructions followed by an address. Many source code statements can yield
unconditional branch IL instructions, but this doesn't mean the statement is a
GOTO. We need to see if we have any unconditional branches to locations where
those locations do nothing, e.g. contain the opcode of NOP.