The MemorySegment::getString overloads should specify how words (e.g. double and quad bytes) are handled in cases where there are no exact matches in size for 16 and 32-bit coded strings (i.e., the last reminder is not looked upon).

Also, multi-byte coding only looks at nulls that are aligned with the particular coding boundaries (e.g. looking for byte {0, 0} only occurs at 16-bit boundaries for UTF-16)