Hi Mike,
The MEMC_CRCONSTR_1 Allocator is incremented when a check constraint is added, default added/changed, decrypt default added/changed or creation of computed column.
These might be key indicators to look into to see if there's any relationship to the 225.
The most common source of 225 error comes from the mismatch of table/view qualifications as discussed in the updated 225 document you referenced. It typically will be seen during some form of normalization or recompile. I've seen this when the procedure cache is severely starved due to concurrent demand and the 225 occurs at runtime.
Dan