FlxSprite.pixelsOverlapPoint and FlxSprite.scale interaction

After you set a FlxSprite's scale to something other than 1.0, FlxSprite.pixelsOverlapPoint() still behaves as if the image is unscaled, which is unintuitive. Is this intended behaviour?

Currently I'm using this function in a subclass of FlxSprite to check the mouse cursor position against the pixels of the scaled image:

public function isCursorOverPixels():Bool {
    var adjustedx = this.getMidpoint().x + (FlxG.mouse.x - this.getMidpoint().x) / this.scale.x;
    var adjustedy = this.getMidpoint().y + (FlxG.mouse.y - this.getMidpoint().y) / this.scale.y;        
    var adjustedCursorPos = new FlxPoint(adjustedx, adjustedy);
    return pixelsOverlapPoint(adjustedCursorPos);
}

You can replace FlxG.mouse.x and FlxG.mouse.y with other desired coords.

It's also odd that FlxSprite's getGraphicMidpoint() returns the midpoint of the image as if it were unscaled, while the parent object FlxObject's getMidpoint() returns the midpoint of the scaled image

Start by reading FlxSprite.pixelsOverlapPoint(), FlxSprite.scale, FlxSprite.getGraphicMidpoint(), and FlxObject.getMidpoint(), then compare how scaled coordinates are handled. Reproduce the discrepancy with a scaled sprite and pointer position; done means the pixel-overlap and midpoint behavior is consistent with the intended scaling semantics or clearly documented if it is intentional.