I find myself in a position where I might need the allow-override-by-assignment behavior that tamperProof() establishes, on a per-property basis (not freezing the entire object).
MarkM, are there any unobvious hazards to refactoring SES's tamperProof to extract that into a separate, exported in cajaVM, function? Particularly, the comments do not explain why tamperProof is constructed by the outer function makeTamperProof. --
