You can have a vector of any movable or copiable type. A common issue, is that a std::vector may relocate its elements in memory when growing, which will result in undefined behaviour if you have sf::Sprite instances pointing to these textures.
If you have a specific issue with a vector of sf::Texture then describe it more precisely, otherwise then just experiment and see by yourself 
Thanks for the reply. I am having an issue with it. As an array, trying to assign a specific, or any, slot to a specific texture causes an instant crash at the point of assigment. Changing to vector creates the same problem. I can convert it to hold an array/vector of sf::Sprite with the Textures assigned, and then all is well. Any idea what the problem could be?
sf::Texture PlantTextures[plantTexNum];
int main(){
PlantTextures[0] = carrotTex;
}
