Spacefractal, it's already feasible and easy -but not recommended normally. By looking closely you will sometimes find that it's o.k. to obfuscate a specific word. Example: GLOBAL emotion$ ...is in use everywhere in the program. You use it to throw and catch messages, communicate between modules. Then have words like "sad", "curious", "in_love" obfuscated as well, it will work. I had a problem when a media name resulted from a concatenation but it was easy to fix: check that the concatenated pieces follow the obfuscation accordingly. The practice has shown me that occasional problems are rare and easy to spot and fix.
Look at the generated code for flip7 (android market) and guess what is what:
FUNCTION a942433508: a942741226%, a942283078% //
ALIAS a942344236 AS a942177478
IF a942177478.a942056186=FALSE
//
IF a942741226>=0 AND a942741226<a942177478.a942996609 AND a942283078>=0 AND a942283078<a942177478.a942047006
ALIAS a942109143 AS a942344236.a942985991[a942283078+(a942344236.a942047006)*a942741226]
IF a942344236.a942619820[a942741226][a942283078]<60 //
//
IF a942908340=FALSE THEN a942599879(a942109143)
//
a942247375(a942741226,a942283078,1) //
ENDIF ; ENDIF
ELSE //
//
//
IF a942741226>=0 AND a942741226<a942344236.a942396132 AND a942283078>=0 AND a942283078<a942344236.a942396132
INC a942344236.a942713984[a942741226][a942283078]
ENDIF
ENDIF
ENDFUNCTION