ByteWeight

the returned memory of symbol is already sorted in an ascending order. 

All iterations over the memory, made with any interfaces are performed in a sorted order, this is intentional. Indeed, for tables, you can also switch the order, if you like.  

I think that it is a good idea to state this explicitly in `Image.memory_of_symbol` function documentation. Feel free to add it yourself, and include it in a PR.