A roadmap for improving Swift performance predictability: ARC improvements and ownership control

There’s currently significant effort being put into UnsafePointer and friends. If the standard library can add bounds checking to the existing types without impacting performance, why introduce another type, forcing clients to decide which one to use and convert between them when someone else has concluded differently?