Well, there are a few limitations that may make it less useful for this purpose:
it's currently limited to 16 bit (but with a auto normalization feature when converting 24bit samples so that you get the full 16 bit range so you don't further reduce the bit depth when compressing unnormalized samples). While editing you might want to retain the full bit depth though.
It has a internal block size of 4096 samples and a lookup table at the beginning to seek to these positions. Seeking to intermediate positions comes with a slight performance penalty (it just decodes the whole block and throws away the unused samples) , but editing may be more tricky because you usually want to cut / truncate samples anywhere.
Actually I fixed this drive-by-style while I was rewriting the parser to support namespaces, so this code will work now:
works(); // "yep"
inline function works()
If you're interested in the gory details, I added a "preparsing" level, which analyses the script and stores the IDs of const vars, reg and inline functions so that the actual parser knows if a variable name is one of the mentioned types.