APDU parser can now interpret count/range READ requests properly

How to interpret a range/count request is unfortunately context
sensitive. :(