[boost] [range]iterator_range test (repost to developer list)

Iterator_range test is failing on practically all platforms. If I understand correctly, it was decided not to treat null-terminated strings differently. If that's the case, why wasn't the test updated? Also, is it true that boost 1.34.1 still supports this behavior? The document says otherwise. I could be confused. Regards, Sean