Changed order of operations in AllocateTextures

If you are reusing the texture of another filter, then by first allocating the textures for the inputFilters before disposing checking if OutputTexture has the correct size, you have a chance that m_TextureOwner.OutputTexture has already been resized to the correct size.

In an even extremer example. If you are only reusing InputRenderTarget and OutputRenderTarget (which is usually the case in the Image Processing script) then those will already have been resized so AllocateTextures doesn't need to do anything, even when you resize the window.

I don't think you'll gain much extra performance this way, but it is nice.