Happy Monday to everyone.

MSDN says:
code that is verifiably type safe:

- A reference to a type is strictly compatible with the type being
referenced.
- Only appropriately defined operations are invoked on an object.
- Identities are what they claim to be.

During the verification process, MSIL code is examined in an attempt to
confirm that the code can access memory locations and call methods only
through properly defined types. For example, code cannot allow an object's
fields to be accessed in a manner that allows memory locations to be
overrun.
Additionally, verification inspects code to determine whether the MSIL has
been correctly generated, because incorrect MSIL can lead to a violation of
the type safety rules. The verification process passes a well-defined set of
type-safe code, and it passes only code that is type safe.
However, some type-safe code might not pass verification because of
limitations of the verification process, and some languages, by design, do
not produce verifiably type-safe code. If type-safe code is required by
security policy and the code does not pass verification, an exception is
thrown when the code is run.
<<<<<<<<<<<

In order to better understand this and see it in action, I would like to
write code that specifically violates these verification requirements.

My question is, can you provide me with code samples that demonstrate how
to:

- allow an object's fields to be accessed in a manner that allows memory
locations to be overrun

- generate incorrect MSIL that would lead to a violation of the type
safety rules

- use type-safe code that does not pass verification because of
limitations of
the verification process, or is written in a
language that, by design, does not produce verifiably type-safe code

Thanks in advance.