Shaggy,
Yes, this constraint goes all the way down to the firmware. Hence we didn't bother adding it to the .NET or Serializer Services interface. Are the additional readings really that useful?
We'll be glad to add this functionality, however, it might be about a month before we can get to it. We have five new products launching over the next 3 weeks, and the Christmas shopping season is on the way, so we're going to be swamped. I will put it on the TODO list, though.
I can just add an optional switch to the 'srf08' command so that you can specify the number of echoes that you want returned. That way it won't break the current interface.
Example:
>srf08 n:17
In the mean time, you should be able to use the Generic I2C interface (either via direct protocol usage, or via the .NET lib) to retrieve the readings. To learn how to do this, please refer to the I2CDevice class under Namespace.RoboticsConnection.Serializer.Sensors topic on the Serializer .NET Library MSDN Help pages.