Graham has passed this on to me to look into. So far it does seem to be a bug in the way our docs are published. I think this function has had a new signature implemented (a non alloc version where you pass in an array to be filled), and the old signature has been obsoleted (where the function returns a new array, and causes memory allocation).
The way our doc build process omits obsoleted functions seems to have tripped over the fact that this function exists with both an obsolete signature and a currently valid signature. I’ll post another update here when I’ve made progress on this.
FYI this also seems to be the case for the similar function “GetOutputData”.