Well, that was what I was doing at first. However, using option 2 causes EntityFieldFactory to create a new object. That uses a case statement to determine which object to create, then calls 'new EntityField()'
So, I was thinking the enum would be way faster use less memory, etc. (The compiler might even do the substituion at compile time, would have to check the IL to see if it is smart enough for that)