> My main issue is not get vs. read... but that the API should imply in a way that the returned buffer needs to be released by the user.

About implying user to release allocated buffer, how about do it like which in `Tizen` by adding `N` at the end?

`unsigned char* FileUtils::allocBufferWithDataFromFileN()`, when user see api that has a `N` suffix, he/she should take care of the allocated buffer and has responsibility to release it.