The minimal value types (MVT) implementation creates Derive Value Type (DVT) from an experiment API for a given "Value Capable Class" (VCC).
Current implementation creates a new value type class with a name mangled from the VCC name as such: "VCC$Value". See:
1) It would be undesirable for "Class.forName()" to be capable of returning such a DVT class.
2) standard core reflection API behavior for such a type doesn't make sense in many cases, e.g. "dvtClass.newInstance()"