BUG - Time remap's last keyframes

Time remapping always sets a keyframe at the first frame of the footage layer, not the in-point, and after the last frame has played. If it set the keyframe at the start of the last frame, you would miss the last frame because time stops before it plays. There is no bug. If the footage is the same length as the comp, you still get every frame. If the footage (or trimmed and pre-composed moving all attributes) footage is shorter than the comp, and you move the last keyframe to slow down the footage, you need to move it 1 frame past the last frame so the last frame of the comp isn't black. If you set a new keyframe at the start of the last frame, and delete the last keyframe, then move the last frame to the end of the comp, you will be missing one frame because time stops before the last frame has played.

If you want to create a loop, you use the "k" key to move to the last keyframe, move back one frame (Ctrl/Cmnd + left arrow), set a new keyframe, then delete the last keyframe because loopOut() plays the last frame of the loop before it starts over. 

There is almost always some confusion with Time Remapping and loopOut(). Once you understand how it works, you should be able to use both tools without problems. 

The equivalent of Time Remapping in other compositing and editing apps works the same way. The start point is the start of the first frame, and the end point is after the last frame has been played.