afInitDataOffset() bug

Hey.. I'm working on ReZound's raw format support and I noticed that 
when afInitDataOffset() is used  when initializing the afSetup, 
afGetFrameCount() still returns the same value as if the data offset was 
zero.  So, you end up trying to read more frames than there are if the 
data offset is given > 0.  

I can easily subtract the offset*frameSize from the reported frame 
count, but I thought it would make more sense for the library to do that.  

Should I do the subtract or submit a patch which fixes the bug for raw 
setups?

Thanks,
  Davy