If you using EOF2.1 (and possibly other versions) and are using inline retain counting on your EOF subclasses, EOF can clobber your retain count when turning your object into a fault. Additionally, EOF reports bogus retain/release events when turning an object into a fault or clearing a fault. To fix both of these problems, you should include the EOFault+OOAFixes.m in your project, both for the development phase and deployment.
This will override two very important methods in EOFault. You will need to include this code in your production application in order to work around the EOF bug. Failure to do so will result in either prematurely deallocated objects (ie, crashes) or inexplicable memory leaks.
Alternatively, you can quit using inline retain counting until a version of EOF is released that does not have this problem.'
EOF2.2: I do not know at this time whether this problem has been fixed in EOF2.2