Better yet, perhaps you could store the byte-code, and pass *that* through an embedded interpreter? (Heck, while you're at it, encrypt the byte-code as well!)
This may help in preventing some clever hacker from attaching to the process via a debugger and capturing the program 's contents as it's being passed for the eval.